Skip to content

[java] Update dependency org.apache.logging.log4j:log4j-core to v2.24.3 #14947

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Dec 27, 2024
Merged

[java] Update dependency org.apache.logging.log4j:log4j-core to v2.24.3 #14947

merged 2 commits into from
Dec 27, 2024

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 27, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.apache.logging.log4j:log4j-core (source) 2.24.1 -> 2.24.3 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added C-java Java Bindings B-dependencies Pull requests that update a dependency file labels Dec 27, 2024
@qodo-merge-pro
Copy link
Contributor

qodo-merge-pro bot commented Dec 27, 2024 •
edited
Loading

CI Failure Feedback 🧐

(Checks updated until commit e0caa69)

Action: Java / Remote Tests (macos) / Remote Tests (chrome, macos)

Failed stage: Pull latest changes [❌]

Failure summary:

The action failed because Git encountered a merge conflict and couldn't automatically determine how
to reconcile divergent branches. This typically happens when:

  • The PR branch has diverged from the target branch
  • Git's pull strategy is not configured
  • Git needs explicit instructions on how to handle the merge (rebase vs. merge)

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  macOS
...

161:  hint:   git config pull.rebase true   # rebase
162:  hint:   git config pull.ff only       # fast-forward only
163:  hint:
164:  hint: You can replace "git config" with "git config --global" to set a default
165:  hint: preference for all repositories. You can also pass --rebase, --no-rebase,
166:  hint: or --ff-only on the command line to override the configured default per
167:  hint: invocation.
168:  fatal: Need to specify how to reconcile divergent branches.
169:  ##[error]Process completed with exit code 128.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @renovate renovate bot force-pushed the renovate/log4j2-monorepo branch from e0caa69 to 17ab74f Compare December 27, 2024 20:28
    @renovate
    Copy link
    Contributor Author

    renovate bot commented Dec 27, 2024

    Edited/Blocked Notification

    Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

    You can manually request rebase by checking the rebase/retry box above.

    ⚠️ Warning: custom changes will be lost.

    @diemol diemol merged commit 2555f14 into trunk Dec 27, 2024
    1 check passed
    @diemol diemol deleted the renovate/log4j2-monorepo branch December 27, 2024 20:46
    sandeepsuryaprasad pushed a commit to sandeepsuryaprasad/selenium that referenced this pull request Mar 23, 2025
    @renovate @selenium-ci @sandeepsuryaprasad
    [java] Update dependency org.apache.logging.log4j:log4j-core to v2.24…
    dd11141 
    ….3 (SeleniumHQ#14947)

* [java] Update dependency org.apache.logging.log4j:log4j-core to v2.24.3

* Repin dependencies

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Selenium CI Bot <[email protected]>
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Reviewers

    No reviews

    Assignees

    No one assigned

    Labels

    B-dependencies Pull requests that update a dependency file C-java Java Bindings

    Projects

    None yet

    Milestone

    No milestone

    Development

    Successfully merging this pull request may close these issues.

    3 participants

    @diemol @selenium-ci